Generating customized documentation for a software product

ABSTRACT

A system and method for creating customized documentation is disclosed. The method comprises storing one or more documents such that each of the one or more documents corresponds to one of a plurality of versions of a software product. The version of the software product which is installed in an installation environment is detected. The configuration of the installation environment is also detected. At least one document from the one or more documents that corresponds to the version of the software product installed in the installation environment is selected. A subset of the selected document that includes the version of the software product installed in the installation environment and the configuration of the installation environment is then determined. A customized document is composed, based on one ore more subsets of the selected document.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.11/740,011, filed Apr. 25, 2007, which application is incorporatedherein by reference in its entirety.

BACKGROUND

1. Field

This disclosure relates to providing documentation customized to theinstalled configuration of a customer's software product.

2. General Background

Documentation for software products is generally not updated after amajor release. For example, a user manual is usually created andreleased with the initial release of the software product, but notupdated with each subsequent fix or software release/update. Newreleases introduce new features and architectural changes that are oftenincomplete. Further, the documentation is often incorrect andincomplete. Accordingly, programmers tend to focus on resolving defectsin the code rather than revising the corresponding product manual. Evenin the case where manuals are updated to accommodate changes or note acommon problem and work around, the work around may no longer berelevant in a version where the problem has been corrected.

Customers are often left to rely upon a customer support team'sknowledge of known defects and/or fixes, which may or may not bedocumented. Customer support attempts to solve these problems outside ofthe product reference documentation stream by creating documents such astechnotes, white papers, and/or training materials. However, thesedocuments are also not maintained as product changes are made, and areoften lost as the product nears the end of its life.

The customer and vendor can be left in a very costly fix cycle whensomething goes wrong late in the implementation life. Both vendors andcustomers experience attrition and incur losses when having to train newpersonnel. It may take a long time for new personnel to learn old tipsand tricks that former experts once held.

Support documents may be available to the customer on a website, orthrough a help application. However, multiple sources provide similartopic documentation, such as incident reports, duplicate defect reports,technotes, training materials, web and online help. When a customer hasa question or problem, a correct answer requires either navigationthrough webpages, technotes, white papers, or released documentation, orreporting of the problem to customer support. Customers may not berunning the current release of the software product and the search mayrequire very specific version and configuration information forresolution.

Additional problems are caused by lack of a single up to date source ofdocumentation. For example, multiple customers report the same defectbecause documentation is incomplete. Multiple information sources createstale and wrong information, which lead to confusion.

SUMMARY

In one aspect, a method of creating customized documentation for asoftware product is disclosed. The method comprises detecting which oneof a plurality of versions of the software product is installed in aninstallation environment. The configuration of the installationenvironment is also detected. At least one document from the one or moredocuments that corresponds to the version of the software productinstalled in the installation environment is selected. A subset of theselected document that includes the version of the software productinstalled in the installation environment and the configuration of theinstallation environment is then determined. A customized document iscomposed, based on one or more subsets of the selected document.

In one aspect, the documents include support documentation on thesoftware product, such as a product manual. The documents may beorganized corresponding to version by being stored in a version controlsystem.

The configuration may be detected automatically by a discoveryapplication, or instead by receiving a selection from a user through oneor more selection menus.

The configuration of the installation environment includes, for example,an operating system associated with the installation environment, one ormore hardware devices associated with the installation environment, orone or more applications associated within the installation environment.

In one aspect, the customized document is composed in response to areport by a customer of an issue with the software product. In oneaspect, the configuration is saved, and the customized document can beautomatically updated based on the saved configuration.

Furthermore, in another aspect, a potential deficiency in the customizeddocument is identified if the issue reported by the customer is notaddressed by the customized document. A corresponding deficiency in thesubset of the selected document from which the customized document wascomposed is then identified. In such an aspect, the selected document isrevised to address the issue with the software product. A determinationmay be made that there is a deficiency in the customized document bymonitoring a counter, the counter having been increased for eachsubsequent report of the same issue.

In another aspect, a system for generating customized documentation isdisclosed. The system comprises a document repository for storing aplurality of documents. Each of the plurality of documents correspondsto one of a plurality of versions of a software product. A discoveryapplication is configured to detect which one of the plurality ofversions of the software product is installed in an installationenvironment. The discovery application is also configured to detect aconfiguration of the installation environment. A document selectionmodule is configured to select a document from the one or more documentsthat corresponds to the version of the software product installed in theinstallation environment. The document selection module further selectsone or more subsets of the document that corresponds to theconfiguration of the installation environment. A document generationmodule is configured to compose a customized document based on the oneor more subsets of the document selected.

According to another aspect of the present disclosure, there is alsoprovided a computer executable program for executing steps of the abovemethods, a machine readable storage medium with codes of the computerexecutable program stored thereon, and a computer program product withcodes of the computer program encoded thereon.

The above and other features and advantages of the present disclosurewill become more apparent from the following detailed description ofpreferred embodiments of the present disclosure taken in conjunctionwith the accompanying drawings.

DRAWINGS

The above-mentioned features and objects of the present disclosure willbecome more apparent with reference to the following description takenin conjunction with the accompanying drawings wherein like referencenumerals denote like elements and in which:

FIG. 1 is a block diagram of a system for generating customizeddocumentation in accordance with one aspect of the disclosure.

FIG. 2 is a flow diagram of a method for generating customizeddocumentation in accordance with one aspect of the present disclosure.

FIG. 3 shows an exemplary embodiment of creating a customized documentin accordance with one aspect of the present disclosure.

FIG. 4 is a flow diagram of a method for generating customizeddocumentation in accordance with one aspect of the present disclosure.

FIG. 5 is a flow diagram of a customer support method in accordance withone aspect of the present disclosure.

FIG. 6 is a block diagram of a system that utilizes customizeddocumentation as implemented in hardware.

DETAILED DESCRIPTION

A system and method of generating customized documentation for aspecific version and configuration of a software product is disclosed.In another aspect, a customer support system and method for respondingto issues reported by a customer by identifying a potential defect inthe software product documentation is disclosed. The system and methodprovide clear problem documentation, which extends throughout a softwareproduct's life cycle (identification, cause, work around, andcorrection). Furthermore, the system and method provide a single sourceof information so that a customer has answers customized to his or herspecific environment.

FIG. 1 illustrates a block diagram of a system 100 in accordance withone aspect of the present disclosure. A software product 110 isinstalled within an installation environment 112. The software productmay be any type of software product, and installed in any type ofinstallation environment. The installation environment refers to boththe physical environment (such as hardware) and the non-physicalenvironment (software, operating system, network configuration) wherethe software product is installed. The software product 110 is generallyinstalled or maintained by a customer 114. Software product 110 may havea plurality of different versions, any one of which may be installed inthe installation environment. Support for the software product 110 isprovided by a vendor 120, usually the same as the developer for thesoftware product. In this example, a documentation system 122 ismaintained by the vendor 120, however the documentation system may bemaintained anywhere. The documentation system 122 comprises a pluralityof documents related to software product 110. Documents are stored in adocument repository 124. The document repository may be a database, orany other data storage system. In one aspect, the documents are storedin a single centralized location. In another aspect, the documents maybe stored in a plurality of different locations.

The documents may come from a plurality of different sources and be of aplurality of different types. For example, one type of document may bethe original product manual. Documents may further comprise releasenotes pertaining to new releases or updates to the software product.Release notes pertain to specific versions of the software. Releasenotes may for example originate from the developers who worked on thecode for the software release.

Another source of documentation is via customers 114 who report aproblem in the software product 110. As shown in FIG. 1, a CustomerRelationship Management (CRM) system 130 may be used by the vendor tocommunicate with customers. Once the problem has been addressed bycustomer support, a document is created detailing the problem reported,and solution. For example, in some instances, a problem will not requirean update to the software, but instead a simple explanation of asolution.

In general, all product communication is recorded within thedocumentation system 122. Regardless of the type or source of thedocument, all documentation is thoroughly categorized according to aplurality of different criteria. As mentioned above, software product110 has a plurality of different versions. Therefore, in one aspect,documentation is categorized based on the version of the softwareproduct to which it pertains.

For example, a software product version 4.3.0.1 may have a defect “X”.Defect “X” is resolved with version 4.3.0.2, but re-introduced with aninterim fix and later resolved in version 4.3.0.3. A customer installingsoftware product version 4.3.0.3 does not need to see any notificationof defect “X’, or documentation related to a work around for defect “X”.However any customer that is running 4.3.0.1 or the interim fix doesneed this documentation, if they are using the component affected.

Therefore, in one aspect, the documentation is entered into a versioncontrol system 126 and is categorized according to its applicability toversion of software product. The version control system may be same orsimilar to those systems used for tracking source code of the softwareproduct itself.

In one aspect, documents are further categorized based upon a pluralityof other criteria. For example, documents may be categorized based uponcriteria relating to the installation environment of the softwareproduct. For example, one type of criteria includes the operating system(OS) on which the software product is installed. Many software productsare developed for more than one operating system or platform, andtherefore the documentation should be tailored according to theoperating system. Furthermore, operating system vendors also continue tomodify releases with patches and may introduce defects and changefeatures that require special instructions from the product vendor. Forexample, a customer using operating systems such as the IBM AIX or Linuxoperating systems should be presented with documentation specific to theAIX or Linux operating system. The documentation does not need toinclude information specific to other operating systems such as theMicrosoft Windows operating system. (IBM and AIX are registeredtrademarks of International Business Machines Corporation in the UnitedStates, other countries, or both. Linux is a registered trademark ofLinus Torvalds in the United States, other countries, or both.Microsoft, Windows, Windows NT, Windows Server, Windows Vista, and theWindows logo are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.)

Other criteria relating to the installation environment includehardware, and applications associated with the installation environment.

In another aspect, the documentation may be further categorizedaccording to the expected audience, or reader of the documentation.Multiple audiences are addressed in documentation, with the addition oftopical level control for skill level or need to know. Some want justthe facts, while others want to be presented with justification for theaction required, impact and future solution. For example, anadministrator of the software product may want technical informationrelated to the installation and maintenance of the software product.However, the end user of a software product may not want as muchtechnical detail, and may not even be concerned with issues such asinstallation.

Documentation could also be categorized according to level of detail.One level may include a brief summary, for those who do not enjoy alengthy explanation. A second level may add more detail or explanationin case the short summary doesn't get the point across.

In yet another aspect, the documentation may be categorized by subjector topic. This may be similar to the topics found in a table ofcontents. This enables the readers of documentation to access theinformation they need quickly.

At some point in time, customer 114 may experience an issue withsoftware product 110. Alternatively, the customer may simply want orneed instructions for configuring or installing a specific aspect of thesoftware product 110. In any case, the customer needs documentationwhich provides support for the software product.

The present disclosure provides a system and method for generating acustomized support document for a software product, the customizedsupport document being tailored at least to the installed version of thesoftware product, and the installation environment of the softwareproduct. Therefore, as shown in FIG. 1, a customized documentationmodule 134 is provided as an interface between vendor and customer. Thecustomized documentation module is configured to generate a customdocument tailored to the specific version and configuration of thecustomer's installation environment. This is accomplished by detectingthe version of the software product 110 installed in the installationenvironment 112, and by detecting a configuration of the installationenvironment 112. Documents, or subsets thereof, from the plurality ofdocuments within the documentation system that match the version of theinstalled software product, and the configuration of the installationenvironment are selected. The documents, and/or subsets thereof arecompiled together as a customized document and presented to thecustomer. The document may for example be compiled in Portable DocumentFormat (PDF), in a web browser as Hypertext Markup Language (HTML), orany other specific documentation/help system format such as EclipseHelp.

FIG. 2 is a flow diagram illustrating the basic steps involved withcreating and maintaining a documentation system in accordance with oneaspect of the disclosure. As mentioned above, a plurality of documentspertaining to a software product are collected from a plurality ofdifferent sources, as indicated at block 210. In one aspect, each of thedocuments is categorized according to which version or versions of aplurality of versions of the software product to which the documentcorresponds. A single document may correspond to a single version of thesoftware product. More than one document may correspond to a singleversion of the software product. Furthermore, a single document maycorrespond to one or more versions of the software product. Therefore,as indicated at block 220, each document is categorized according to theversion of software product to which it corresponds.

The documents are further categorized according to other criteria, whichare defined depending on the software product and vendor. Examples ofother criteria include criteria relating to the installation environmentof the software product, such as operating system, hardware, andapplications present or associated with the installation environment.Documents are thereby categorized by configuration criteria, asindicated at block 230. Criteria may also include customer definedaspects such as audience and level of detail. In one aspect, a documentindex is also created, as indicated at block 240. The document index maybe similar to a table of contents.

The act of categorizing or classifying the documentation may beaccomplished in many different ways. FIG. 3 illustrates one example ofhow a document may be structured, and thereby categorized in order tocreate a customized document in accordance with the present disclosure.

As mentioned above, a document may correspond to one or more versions ofthe software product. For example, some material may be relevant to morethan one version of the software, and may not require being duplicatedor revised in view of subsequent versions. Also, there may be more thanone document that relates to each version of the software product.

In one aspect, a document is divided into a plurality of subsets. Eachof the subsets corresponds to a certain criteria. For example, in theexample shown in FIG. 3, a document 310 contains informationcorresponding to version 1.2 of the software product. In this example,the document 310 contains information which can be categorized accordingto three different criteria. A first criteria 320 includes the type ofoperating system on which the software program is installed. In theexample shown, the software product can operate on an AIX operatingsystem or a Linux operating system. Document 310 contains documentationinformation relevant to both the AIX and Linux operating systems.However, in this case, information pertaining to the AIX operatingsystem is located in one subset 322 of the document, and informationpertaining to the Linux operating system is contained within anothersubset 324. Only the subset relevant to the customer's installedoperating system is selected to be included in the customized document.

A second criteria 330 includes specific hardware elements associatedwith the installation environment of the software product. For example,Hardware A and Hardware B are hardware elements that may be found to beassociated with an installation environment of the software product.Perhaps there are known issues with the interaction between Hardware Aand version 1.2 of the software product. This information would bebeneficial to a customer using Hardware A, yet not relevant to thosecustomers using Hardware B. As noted in FIG. 3, information pertainingto Hardware A is located within subset 332, while information pertainingto Hardware B is located within subset 334 of document 310.

A third criteria 340 includes one or more applications associated withthe installation environment of the software product. Similar to theinteraction with hardware elements, there may be known issues with othersoftware products or applications of which a customer should be madeaware. Therefore, information related to each specific application isdivided into subsets as well (342, 344, 346).

In the example shown in FIG. 3, a customer having installed version 1.2of a software product operating on Linux, with Hardware elements “A”installed, and Applications “A” and “B” present in the installationenvironment is detected. A customized document is generated based onthis configuration. Therefore, subsets 324, 332, 342, and 344, whichcorrespond to the above mentioned configuration are collected andcompiled in a customized document 350.

In one aspect, a document is simply a file containing text. Eachdocument may contain a plurality of portions or subsets. Each portion orsubset of a document may pertain to any one of the above mentionedcriteria. Subsets and criteria may be indicated by the use of tagswithin the document to indicate the start and end of a specific subset.A document may be a single file, or multiple files.

Of course, there are many other ways to structure the information. Forexample, a database could be used to index and categorize documentation.In this case, the term document may instead be defined as a databaseentry.

FIG. 4 is a flow diagram of the basic steps involved in creating acustomized document according to the configuration of the softwareproduct. As indicated at block 410, the version of the software productinstalled in an installation environment is detected. The configurationof the installation environment is also detected, as indicated at step420.

In one aspect, a discovery application is provided to automaticallydetect the configuration of the software product within its installationenvironment. For example, a customer may be able to download a discoveryapplication to his or her computer. The application is designed toanalyze the configuration of the installation environment of thesoftware product. For example, in one aspect the application isconfigured to automatically determine the version of the softwareproduct that is installed. In another aspect, the application alsodetects the configuration of the installation environment as defined byvarious criteria. For example, this criteria may include the operatingsystem (and applicable version thereof) of the installation environment.In yet another aspect, the application analyzes the type(s) of hardwareof the installation environment. This may for example include processor,video card, main board, memory, network card, etc. If the softwareproduct interacts with other software products, the discoveryapplication may be configured to detect the presence of other softwareproducts with which it interacts.

In another aspect, the configuration may be detected through a manualselection by a user. For example a configuration could be chosen througha series of drop down menus. In one aspect, the configuration processproduces a style list that is built from a bill of materials or optionstemplate.

Once the configuration of the software product and its installationenvironment has been provided, documents corresponding to the detectedversion of the software product are selected, as indicated at step 430.Next, documents, or subsets thereof, are selected which specificallycorrespond to the configuration of the installation environment, asindicated at step 440.

Depending on the structure of the document, this could involve a selectstatement from a database. Alternatively this could involve searchingfor tags within a document which specify the location of each subset ofinformation.

As indicated by step 450, in one aspect, additional criteria may also beoptionally specified by the customer. The customized document iscompiled at step 450. In one aspect, a build process reads theconfiguration and compiles custom document(s) in PDF, HTML, and/or otherformats.

In one aspect, the customized documentation may comprise the originalsoftware product manual as a base. In addition, however, all releasenotes specific to the version installed are added to the manual. Theymay be added at the end, or intermingled with the manual. Also, anydefect reports relevant to the configuration may be added.

In one aspect, the customized document is made specific to thecustomer's defined environment and kept current using all reportedproblems. This may be accomplished by saving the detected configurationof the customer's software product, and monitoring for changes matchingthe configuration. As new problems are reported, a problem detail ornotification is made if relevant to the current configuration.

Updates notices are received, and depending on configuration are eithercompiled in document per above compile step or notified with configuredmethod similar to a software fix process. This is quite differentbecause a software fix process often leaves many unused documentationfiles, and the fix process is very specific to the configuration.

In another aspect of the disclosure, a customer support system andmethod for responding to issues reported by a customer by identifying apotential defect in the software product documentation is disclosed. Inother words, issues with a software product are addressed by treatingthe issue as a defect in the software product's documentation andupdating the documentation accordingly.

Traditional customer support systems and methods tend to identify anissue or defect with a software product and work to address the issue ordefect. However, once the issue has been addressed for the customer, thecustomer support process usually ends there. Often, the documentation isnot updated to address the problem, and thereby, the documentationcannot prevent other customers from experiencing the same problem.Furthermore, even if the documentation is updated, there is no good wayof providing other customers with such updates to the documentation.This is a significant problem in customer support. The same issue getsreported over and over by multiple customers, and can be quite timeconsuming. However, by using the product documentation as reference incommunications and considering that every problem with a softwareproduct requires improvement in the software product's documentation,the cycle can be corrected.

Basic steps are as follows:

1. Customer Support process categorizes a customer problem or questionand resolves. However, the problem is not just identified in thesoftware product, but as a defect in the documentation.

2. Problem categorization process finds or creates and indexes areference to existing document(s).

3. A resolution is recorded or updated in the document.

FIG. 5 illustrates one aspect of a customer support method in accordancewith the present disclosure. Consider a customer has an issue with aninstalled software product, as is indicated at block 510. The customermay first be provided with the option of providing a customized set ofdocumentation (as has been described thus far) before reporting thespecific issue to customer support. As described above, theconfiguration of the customer's installation environment is detected, asindicated at block 520. This may either be accomplished through adiscovery application configured to automatically detect theconfiguration of the software product and its installation environment,or through a manual process such as user selection through a pluralityof menus. Based on the detected version of the software product and theconfiguration of installation environment, a customized set ofdocumentation is generated, as indicated at block 530. The customizedset of documentation is specific to the detected version of the softwareproduct as installed, and is further specific to the detectedconfiguration of the installation environment (operating system,hardware, etc) The documentation may further optionally be tailored touser selected criteria such as a specific topic, level of detail,audience, etc.

As indicated by decision block 535, the issue may or may not be resolvedthrough the generation of customized support documentation. In an idealsituation, the issue, as well as a detailed solution, is describedwithin the customized document, and the customer support inquiry ends atblock 590. However, if the customer is not provided with an adequatesolution to their issue, the issue must still be addressed by customersupport. Therefore, if the issue is not adequately addressed for thecustomer in the customized documentation, the issue is reported tocustomer support for further investigation at step 540.

It should be understood that several of these steps may occur indifferent orders. For example in another aspect, the customer reportsthe issue to customer support (block 540) first, and the customizeddocumentation is generated (block 530) after submitting the issue tocustomer support.

At decision block 555, customer support determines whether or not theissue reported by the customer is a known issue.

For example, the issue may have previously been reported by anothercustomer, and is in the process of being resolved. Or in anotherexample, there simply may be no discussion of the issue within thedocumentation. In another aspect, the issue may be discussed in thedocumentation, however the solution is not a good or proper explanation.Another problem might arise in difficulty in finding the informationwith the documentation. The proper solution may be present in thedocumentation, but not located in the right place such that a customercan locate the information easily.

Regardless, if the issue is a known issue, customer support attempts toidentify a portion of the documentation to which the issue shouldcorrespond.

In one aspect, a counter is incremented each time a known issue isreported. The counter would identify a portion of the documentation.

Therefore, customer support could monitor the number of times an issuehas arisen in a specific area of documentation, and could thereby makethe decision that appropriate measures should be taken to revise thatarea of the documentation.

If it is determined that the document does not adequately address theissue, the document is revised, as indicated at step 584.

At decision block 555, customer support determines whether or not theissue reported by the customer is a known issue.

For example, the issue may have previously been reported by anothercustomer, and is in the process of being resolved. Or in anotherexample, there simply may be no discussion of the issue within thedocumentation. In another aspect, the issue may be discussed in thedocumentation, however, the solution is not a good or properexplanation. Another problem might arise in difficulty in finding theinformation with the documentation. The proper solution may be presentin the documentation, but not located in the right place such that acustomer can locate the information easily.

Regardless, if the issue is a known issue, customer support attempts toidentify a portion of the documentation to which the issue shouldcorrespond.

In one aspect, a counter is incremented each time a known issue isreported. The counter would identify a portion of the documentation.

Therefore, customer support could monitor the number of times an issuehas arisen in a specific area of documentation, and could thereby makethe decision that appropriate measures should be taken to revise thatarea of the documentation.

If it is determined that the document does not adequately address theissue, the document is revised, as indicated at step 584.

If at decision block 555, the issue is determined to be a new or unknownissue, customer support first works to research and resolve the issue,as indicated at block 580. Once the issue has been addressed for thecustomer, either with a work around, or a fix to the software product,the issue is then addressed in the documentation. Because this issue isnew or unknown, it is likely there is no mention of the issue within thedocumentation. The documentation is therefore revised accordingly,whether that involves updating an existing document to include newinformation, or creating a new document pertaining to the issue reportedby the customer.

The documentation system therefore provides a single source ofinformation that is appropriate for the customer by generating acustomized document that is specific to the customer's environment. Theenvironment can be either defined or discovered with an automatedapplication. The documentation system also solves costly multiplecustomer support problem reports for the same defect by providingsolutions to defects in documentation. Further, the documentation systemprovides a method of automation or user configuration selection, thecustomer environment is stored so that out of scope information isminimized. Customer specific easy to follow documentation is provided bythe addition of customer specific configuration. In addition, thedocumentation system provides a process and structure to provide up tothe minute customer implementation specific documentation. Thedocumentation system avoids broadcasting, to the market, the number andtype of defects with large number of technotes. Further, thedocumentation system solves customer's problem or answers the questionbefore a problem management report is opened in the customerrelationship management system. In addition, the documentation systemprovides an approach which allows customer support to solve a problemonce. The documentation system also documents the defects and workarounds that the customer needs with updates to remove old work arounds.

The documentation system provides a process for product documentationwhen product life cycle changes. When product documentation is releasedand is planned to be removed from marketing, the ownership of thepublications are moved to the Support Organization or a new role withinInformation Development that allows frequent quick turn changes to bedictated from support and released on demand. Further, the documentationsystem enables the end user to customize the product documentation andallow for dynamic updates. In addition, the documentation system allowssupport to correct documentation defects and enhancements before problemclosure, or an index to where the problem closure was documented isrecorded.

Customer problem closure is utilized by documentation index keyreferences to the document where the problem summary is documented.Resolution or work around may have different life cycle and whenavailable are found using this same index key. Use of an index keyenables clear documentation of the problem, provides environment andconfiguration, and allows extensions so it can be added to existingelectronic collections and submission tools.

Customer configuration information enables detail usage feedback so thatcontemplated changes may be recorded for better risk assessments,migration proposals, and product planning. In general, problem hotspotscan quickly be located, analyzed, and corrected.

FIG. 6 illustrates a block diagram of a system 600 that generatescustomized documentation for a user's specific software productconfiguration. In one embodiment, the system 600 is suitable for storingand/or executing program code and is implemented using a general purposecomputer or any other hardware equivalents. Thus, the system 600comprises a processor 602, a memory 606, e.g., random access memory(“RAM”) and/or read only memory (“ROM”), a component recycling module608, and various I/O devices 604.

The processor 602 is coupled, either directly or indirectly, to thememory 606 through a system bus. The memory 606 can include local memoryemployed during actual execution of the program code, bulk storage,and/or cache memories which provide temporary storage of at least someprogram code in order to reduce the number of times code must beretrieved from bulk storage during execution.

The I/O devices 604 can be coupled directly to the system 600 or throughintervening input/output controllers. Further, the I/O devices 604 caninclude a keyboard, a keypad, a mouse, a microphone for capturing speechcommands, a pointing device, and other user input devices that will berecognized by one of ordinary skill in the art. Further, the I/O devices604 can include a receiver, transmitter, speaker, display, image capturesensor, biometric sensor, etc. In addition, the I/O devices 604 caninclude storage devices such as a tape drive, floppy drive, hard diskdrive, compact disk (“CD”) drive, etc.

Network adapters may also be coupled to the system 600 to enable thesystem 600 to become coupled to other systems, remote printers, orstorage devices through intervening private or public networks. Modems,cable modems, and Ethernet cards are just a few of the currentlyavailable types of network adapters.

It should be understood that the method and system described herein cantake the form of an entirely hardware embodiment, an entirely softwareembodiment, or an embodiment containing both hardware and softwareelements. If software is utilized to implement the method or system, thesoftware can include, but is not limited to, firmware, residentsoftware, microcode, etc.

Further, the method and/or system can take the form of a computerprogram product accessible from a computer-usable or computer-readablemedium providing program code for use by or in connection with acomputer or any instruction execution system. For the purpose of thisdescription, a computer-usable or computer readable medium can be anyapparatus that can contain, store, communicate, propagate, or transportthe program for use by or in connection with the instruction executionsystem, apparatus, or device.

The medium can be an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system (or apparatus or device) or apropagation medium. Examples of a computer-readable medium include asemiconductor or solid state memory, magnetic tape, a removable computerdiskette, a RAM, a ROM, a rigid magnetic disk and an optical disk.Current examples of optical disks include CD-read only memory(“CD-ROM”), CD-read/write (“CD-R/W”) and DVD.

While the apparatus and method have been described in terms of what arepresently considered to be the most practical and preferred embodiments,it is to be understood that the disclosure need not be limited to thedisclosed embodiments. It is intended to cover various modifications andsimilar arrangements included within the spirit and scope of the claims,the scope of which should be accorded the broadest interpretation so asto encompass all such modifications and similar structures. The presentdisclosure includes any and all embodiments of the following claims.

The invention claimed is:
 1. A computer program product comprising acomputer-readable storage medium having a computer readable program,wherein the computer readable program when executed on a computer causesthe computer to: detect which one of a plurality of versions of asoftware product is installed in an installation environment; detect aconfiguration of the installation environment; select a document fromone or more documents that corresponds to the version of the softwareproduct installed in the installation environment; determine a subset ofthe selected document that includes the version of the software productinstalled in the installation environment and the configuration of theinstallation environment; and compose a customized document based on thesubset of the selected document.
 2. The computer program product ofclaim 1 wherein the one or more documents include support documentationon the software product.
 3. The computer program product of claim 1wherein the configuration of the installation environment is detectedautomatically by a discovery application.
 4. The computer programproduct of claim 1 wherein the configuration of the installationenvironment is detected automatically by receiving a selection from auser through one or more selection menus.
 5. The computer programproduct of claim 1 wherein the configuration of the installationenvironment includes an operating system associated with theinstallation environment.
 6. The computer program product of claim 1wherein the configuration of the installation environment includes alisting of one or more hardware devices associated with the installationenvironment.
 7. The computer program product of claim 1 wherein theconfiguration of the installation environment includes a listing of oneor more applications associated within the installation environment. 8.The computer program product of claim 1 wherein the one or moredocuments are stored in a version control system.
 9. The computerprogram product of claim 1 wherein a determination is made that there isa deficiency in the customized document by monitoring a counter, thecounter having been increased for each subsequent report of a sameissue.
 10. A method comprising: detecting, with a processor of acomputer, which one of a plurality of versions of a software product isinstalled in an installation environment; detecting a configuration ofthe installation environment; selecting a document from one or moredocuments that corresponds to the version of the software productinstalled in the installation environment; determining a subset of theselected document that includes the version of the software productinstalled in the installation environment and the configuration of theinstallation environment; and composing a customized document based onthe subset of the selected document.
 11. The method of claim 10 whereinthe one or more documents include support documentation on the softwareproduct.
 12. The method of claim 10 wherein detecting the configurationof the installation environment is performed automatically by adiscovery application.
 13. The method of claim 10 wherein detecting theconfiguration of the installation environment is performed by receivinga selection from a user through one or more selection menus.
 14. Themethod of claim 10 wherein the configuration of the installationenvironment includes an operating system associated with theinstallation environment.
 15. The method of claim 10 wherein theconfiguration of the installation environment includes a listing of oneor more hardware devices associated with the installation environment.16. The method of claim 10 wherein the configuration of the installationenvironment includes a listing of one or more applications associatedwithin the installation environment.
 17. The method of claim 10 whereinthe one or more documents are stored in a version control system. 18.The method of claim 10 wherein a determination is made that there is adeficiency in the customized document by monitoring a counter, thecounter having been increased for each subsequent report of a sameissue.
 19. A system comprising: a processor; and memory coupled to theprocessor, wherein the memory stores a computer program, and wherein thecomputer program is executable by the processor to: detect which one ofa plurality of versions of a software product is installed in aninstallation environment; detect a configuration of the installationenvironment; select a document from one or more documents thatcorresponds to the version of the software product installed in theinstallation environment; determine a subset of the selected documentthat includes the version of the software product installed in theinstallation environment and the configuration of the installationenvironment; and compose a customized document based on the subset ofthe selected document.
 20. The system of claim 19 wherein a documentselection module that selects the document comprises a database engine.21. The system of claim 19 wherein the one or more documents includesupport documentation on the software product.
 22. The system of claim19 wherein the configuration of the installation environment includes anoperating system associated with the installation environment.
 23. Thesystem of claim 19 wherein the configuration of the installationenvironment includes a listing of one or more hardware devicesassociated with the installation environment.
 24. The system of claim 19wherein the configuration of the installation environment includes alisting of one or more applications associated within the installationenvironment.
 25. The system of claim 19 wherein the one or moredocuments are stored in a version control system.
 26. The system ofclaim 19 wherein a determination is made that there is a deficiency inthe customized document by monitoring a counter, the counter having beenincreased for each subsequent report of a same issue.